Skip to content

chore: Migrate RL Scanner to usable actions#888

Merged
tanya732 merged 3 commits into
masterfrom
chore/migrate-rl-scanner-to-useable-action
Jul 3, 2026
Merged

chore: Migrate RL Scanner to usable actions#888
tanya732 merged 3 commits into
masterfrom
chore/migrate-rl-scanner-to-useable-action

Conversation

@tanya732

@tanya732 tanya732 commented Jul 1, 2026

Copy link
Copy Markdown
Contributor

Changes

  • Replaced the local .github/actions/rl-scanner composite action with the shared rl-scan@main action in the existing rl-scanner.yml reusable workflow.
  • Wired the newly required secrets, SIGNAL_HANDLER_DOMAIN and PRODSEC_PYTHON_TOOLS_REPO, through release.yml and rl-scanner.yml.
  • Fixed the artifact path ($(pwd)${{ github.workspace }}) so the scanner can locate the built .tgz artifact.
  • Removed the obsolete local composite action.

@tanya732 tanya732 requested a review from a team as a code owner July 1, 2026 11:27
@tanya732 tanya732 changed the title chore: Migrate RL Scanner to useable actions chore: Migrate RL Scanner to usable actions Jul 1, 2026

@kailash-b kailash-b left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We can consider getting rid of the rl-scanner.yml and just integrate the one step directly in release.yml.

@tanya732 tanya732 merged commit 4eec7aa into master Jul 3, 2026
6 of 7 checks passed
@tanya732 tanya732 deleted the chore/migrate-rl-scanner-to-useable-action branch July 3, 2026 09:50
@tanya732

tanya732 commented Jul 3, 2026

Copy link
Copy Markdown
Contributor Author

@kailash-b Thank you for the review

I looked into inlining it, but rl-scanner.yml isn't really a single step, it's a full build+package pipeline. Inlining would move all of that into release.yml as a job and roughly double its length, mixing the release orchestration with the scanner's build plumbing. So I'd slightly lean toward leaving it split for better readability and open to revisiting if we consolidate later.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants